Skip to content

Conversation

@jonburdo
Copy link
Contributor

@jonburdo jonburdo commented Nov 25, 2025

Enables MCPRegistry resources to use PersistentVolumeClaims as a data source in addition to existing ConfigMap, Git, and API sources.

🤖 Generated with Claude Code

Large PR Justification

  • Auto-generated docs
  • a couple of large example registry files

@codecov
Copy link

codecov bot commented Nov 25, 2025

Codecov Report

❌ Patch coverage is 90.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.59%. Comparing base (20ecb03) to head (b71ed3d).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...md/thv-operator/pkg/registryapi/podtemplatespec.go 89.47% 2 Missing ⚠️
cmd/thv-operator/pkg/registryapi/config/config.go 90.90% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2719      +/-   ##
==========================================
+ Coverage   56.55%   56.59%   +0.03%     
==========================================
  Files         320      320              
  Lines       30874    30901      +27     
==========================================
+ Hits        17460    17487      +27     
  Misses      11911    11911              
  Partials     1503     1503              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@dmartinol dmartinol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution!
I commented with some concerns about using the configured values, please TAL!

@github-actions github-actions bot added the size/L Large PR: 600-999 lines changed label Nov 25, 2025
@dmartinol
Copy link
Collaborator

Need some adjustment to adapt to the new model:

  • naming review
  • multiple registries (FKA source)
    The latter implies that the mounted path should use the regisstry name to create a sub-folder.
    Finally, it would be great if you can extend the existing IT with this use case (maybe having a config with both ConfigMap and PVC)

@jonburdo jonburdo marked this pull request as draft November 26, 2025 03:27
@jonburdo jonburdo force-pushed the pvc-source branch 3 times, most recently from 27c80e2 to 632f5b0 Compare November 27, 2025 03:59
@jonburdo jonburdo marked this pull request as ready for review November 27, 2025 04:02
Copy link
Collaborator

@dmartinol dmartinol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please take a look at the REGISTRY.md file to include the new registry type (BTW: if you can, please also replace the "data sources" to "registries", it's another leftover of previous PRs

@jonburdo
Copy link
Contributor Author

jonburdo commented Dec 1, 2025

A few notes:

  • I changed the mount path to simply use the pvc claim name instead of registry name ({RegistryJSONFilePath}/{claimName}/) for the mount path, since a single pvc could contain multiple registry files.
  • I suggest switching "source" to "registry" in a followup to narrow the scope. I'm happy to do this - tracked in Rename Source to Registry #2815

@github-actions github-actions bot removed the size/L Large PR: 600-999 lines changed label Dec 1, 2025
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Large PR Detected

This PR exceeds 1000 lines of changes and requires justification before it can be reviewed.

How to unblock this PR:

Add a section to your PR description with the following format:

## Large PR Justification

[Explain why this PR must be large, such as:]
- Generated code that cannot be split
- Large refactoring that must be atomic
- Multiple related changes that would break if separated
- Migration or data transformation

Alternative:

Consider splitting this PR into smaller, focused changes (< 1000 lines each) for easier review and reduced risk.

See our Contributing Guidelines for more details.


This review will be automatically dismissed once you add the justification section.

@github-actions github-actions bot added the size/XL Extra large PR: 1000+ lines changed label Dec 1, 2025
Copy link
Collaborator

@dmartinol dmartinol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm apart few minor docs to review

@jonburdo jonburdo force-pushed the pvc-source branch 2 times, most recently from 5934fdf to b71ed3d Compare December 1, 2025 13:30
@jonburdo
Copy link
Contributor Author

jonburdo commented Dec 1, 2025

I fixed the docs and then rebased.

I switched back to using registryName for the mount path, which means that if we have two registry files in a single pvc, it has to be mounted multiple times. I had tried using claimName instead of registryName and that allows for each pvc to be mounted just once, but it requires more test refactoring and changes expectations compared with the existing configMap approach.

dmartinol
dmartinol previously approved these changes Dec 1, 2025
Copy link
Collaborator

@dmartinol dmartinol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@github-actions github-actions bot added size/XL Extra large PR: 1000+ lines changed and removed size/XL Extra large PR: 1000+ lines changed labels Dec 1, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 1, 2025

✅ Large PR justification has been provided. The size review has been dismissed and this PR can now proceed with normal review.

@github-actions github-actions bot dismissed their stale review December 1, 2025 14:22

Large PR justification has been provided. Thank you!

Enables MCPRegistry resources to use PersistentVolumeClaims as a data
source in addition to existing ConfigMap, Git, and API sources.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
Signed-off-by: Jon Burdo <[email protected]>
@dmartinol dmartinol enabled auto-merge (squash) December 1, 2025 15:29
@dmartinol dmartinol merged commit 6a9a2c1 into stacklok:main Dec 1, 2025
@jonburdo jonburdo deleted the pvc-source branch December 1, 2025 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XL Extra large PR: 1000+ lines changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants